Systems and methods for initiating external actions via a group-based communication system

ABSTRACT

A group-based communication platform may be utilized to execute one or more processing actions via respective external application systems based on messages exchanged among client devices via the group-based communication platform. A particular processing action may be executed for a particular message by generating a container including contextual data and payload data, wherein the payload data comprises the message for which the processing action is to be performed. The container is provided to the external application system via a proxy endpoint, thereby causing the external application system to execute the processing action based on the data included within the container.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No.16/206,542, filed Nov. 30, 2018, which issued as U.S. Pat. No.10,348,655 on Jul. 9, 2019, which is a continuation of U.S. applicationSer. No. 16/176,883, filed on Oct. 31, 2018, which issued as U.S. Pat.No. 10,701,003 on Jun. 30, 2020, which claims priority from U.S.Provisional Application Ser. No. 62/674,491, filed May 21, 2018, all ofwhich are incorporated herein by reference in their entirety.

BACKGROUND

Systems have been provided for exchanging and consolidating messageswithin a communications interface among a plurality of client devicesand external systems via an at least partially centralized messagingserver system.

Through applied effort, ingenuity, and innovation many deficiencies ofsuch systems have been solved by developing solutions that are inaccordance with the embodiments of the present invention, many examplesof which are described in detail herein.

BRIEF SUMMARY

Various embodiments are directed to systems and methods for enablingsubstantive interactions between a group-based communication platformand one or more external systems, thereby enabling the group-basedcommunication platform to perform various functions within thoseexternal systems.

Various embodiments are directed to a computer-implemented method forexecuting processing actions based on messages within an externalapplication system. In certain embodiments, the method comprises,generating, via one or more processors of a group-based communicationplatform, a container comprising contextual data and payload data,wherein the contextual data is generated based at least in part on adata stored within a processing action table and identifies (1) aprocessing action to be performed by an external application system and(2) a client token identifying a client device requesting the processingaction, and the payload data comprises a message exchanged via thegroup-based communication platform; providing, via the one or moreprocessors of the group-based communication platform, the container to aproxy endpoint accessible to the external application system to enablethe external application system to retrieve data within the containerand to execute the identified processing action based at least in parton the payload data; receiving, via the one or more processors of thegroup-based communication platform, a response from the externalapplication system, wherein the response comprises the client tokenidentifying the client device requesting the processing action; based atleast in part on the response, causing the client device to display aninteractive dialog; receiving additional data from the client device viathe interactive dialog; and transmitting the additional data to theproxy endpoint to be associated with the container to enable theexternal application system to utilize the additional data to executethe processing action.

In certain embodiments, the method further comprises receiving aconfirmation response from the external application system indicatingcompletion of the requested processing action; and transmitting aconfirmation message to the requesting client device. In certainembodiments, the confirmation message is transmitted to the clientdevice as a message. Moreover, in various embodiments, the message isshared between a plurality of client devices within a communicationchannel via the group-based communication platform, wherein thecommunication channel has an associated channel identifier. In suchembodiments, the method further comprises: causing the client device todisplay a curated list of a plurality of processing actions, wherein theprocessing actions included within the curated list are selected basedat least in part on a channel identifier; and receiving input from theclient device selecting the processing action to be performed.

Moreover, the message may associated with one or more characteristics.In such embodiments, the method further comprises: causing the clientdevice to display a curated list of a plurality of processing actions,wherein the processing actions included within the curated list areselected based at least in part on the characteristics associated withthe message; and receiving input from the client device selecting theprocessing action to be performed. Moreover, the characteristicsassociated with a message may identify a sending user identifier of themessage, and wherein the processing actions included within the curatedlist are selected based at least in part on the sending user identifierof the message. In certain embodiments, the message comprises at leastone of: a text-based message or a file object.

Various embodiments are directed to a system configured for executing aprocessing action based on a message shared via a group-basedcommunication platform within an external application system. In certainembodiments, the group-based communication platform comprises: one ormore non-transitory memory storage repositories, wherein the one or morenon-transitory memory storage repositories comprise a processing actiontable identifying one or more processing actions available for one ormore messages; and one or more processors, wherein the one or moreprocessors are collectively configured to: receive a selection of amessage and a processing action for the message from a client device,wherein the processing action is selected from the processing actiontable; generate a container comprising contextual data and payload databased upon the selection of the message and the processing action forthe message, wherein the contextual data is generated based at least inpart on a data stored within a processing action table and identifies(1) a processing action to be performed by an external applicationsystem and (2) a client token identifying the client device requestingthe processing action, and the payload data comprises a messageexchanged via the group-based communication platform; provide thecontainer to a proxy endpoint accessible to the external applicationsystem to enable the external application system to retrieve data withinthe container and to execute the identified processing action based atleast in part on the payload data; receive, a response from the externalapplication system, wherein the response comprises the client tokenidentifying the client device requesting the processing action; based atleast in part on the response, cause the client device to display aninteractive dialog; receive additional data from the client device viathe interactive dialog; and transmit the additional data to the proxyendpoint to be associated with the container to enable the externalapplication system to utilize the additional data to execute theprocessing action.

In various embodiments, the one or more processors are furtherconfigured to: receive a confirmation response from the externalapplication system indicating completion of the requested processingaction; and transmit a confirmation message to the requesting clientdevice. In certain embodiments, the confirmation message is transmittedto the client device as a message. Moreover, the message may be sharedbetween a plurality of client devices within a communication channel viathe group-based communication platform. In such embodiments, thecommunication channel has an associated channel identifier and whereinthe one or more processors are further configured to: cause the clientdevice to display a curated list of a plurality of processing actions,wherein the processing actions included within the curated list areselected based at least in part on a channel identifier; and wherein theselection of the processing action is based at least in part on thecurated list of a plurality of processing actions.

In various embodiments, the message is shared between a plurality ofclient devices within a communication channel via the group-basedcommunication platform. In such embodiments, the communication channelhas an associated channel identifier and wherein the one or moreprocessors are further configured to: cause the client device to displaya curated list of a plurality of processing actions, wherein theprocessing actions included within the curated list are selected basedat least in part on characteristics associated with the message; andwherein the selection of the processing action is based at least in parton the curated list of a plurality of processing actions. Moreover, thecharacteristics associated with a message may identify a sending useridentifier of the message, and the processing actions included withinthe curated list may be selected based at least in part on the sendinguser identifier of the message. Moreover, the message may comprise atleast one of: a text-based message or a file object.

Certain embodiments are directed to a computer program product forexecuting a processing action based on a message within an externalapplication system, the computer program product comprising at least onenon-transitory computer-readable storage medium having computer-readableprogram code portions stored therein. In certain embodiments, thecomputer-readable program code portions comprising an executable portionconfigured to: generate a container comprising contextual data andpayload data, wherein the contextual data is generated based at least inpart on a data stored within a processing action table and identifies(1) a processing action to be performed by an external applicationsystem and (2) a client token identifying a client device requesting theprocessing action, and the payload data comprises a message exchangedvia the group-based communication platform; provide the container to aproxy endpoint accessible to the external application system to enablethe external application system to retrieve data within the containerand to execute the identified processing action based at least in parton the payload data; receive a response from the external applicationsystem, wherein the response comprises the client token identifying theclient device requesting the processing action; based at least in parton the response, cause the client device to display an interactivedialog; receive additional data from the client device via theinteractive dialog; and transmit the additional data to the proxyendpoint to be associated with the container to enable the externalapplication system to utilize the additional data to execute theprocessing action.

In certain embodiments, the executable portions are further configuredto: receive a confirmation response from the external application systemindicating completion of the requested processing action; and transmit aconfirmation message to the requesting client device. Moreover, theconfirmation message may be transmitted to the client device as amessage.

In certain embodiments, the message is shared between a plurality ofclient devices within a communication channel via the group-basedcommunication platform, and in such embodiments the communicationchannel has an associated channel identifier and wherein the computerprogram product further comprises an executable portion configured to:cause the client device to display a curated list of a plurality ofprocessing actions, wherein the processing actions included within thecurated list are selected based at least in part on a channelidentifier; and receive input from the client device selecting theprocessing action to be performed.

In various embodiments, the message is associated with characteristics,and in such embodiments the computer program product further comprisesan executable portion configured to: cause the client device to displaya curated list of a plurality of processing actions, wherein theprocessing actions included within the curated list are selected basedat least in part on the characteristics associated with the message; andreceive input from the client device selecting the processing action tobe performed. Moreover, the characteristics associated with a messagemay identify a sending user identifier of the message, and theprocessing actions included within the curated list may be selectedbased at least in part on the sending user identifier of the message. Incertain embodiments, the message comprises at least one of: a text-basedmessage or a file object.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 illustrates a schematic view of a system 100 encompassing agroup-based communication platform in communication with one or moreclient devices in accordance with one embodiment.

FIG. 2 illustrates an apparatus 200 of a message distribution server(s)110 in accordance with one embodiment.

FIG. 3 illustrates a flowchart 300 for loading a processing action for agroup-based communication platform in accordance with one embodiment.

FIG. 4 illustrates a wireframe 400 providing a development portal forproviding a processing action via a group-based communication platformin accordance with one embodiment.

FIG. 5 illustrates a wireframe 500 providing a development portal forproviding a processing action via a group-based communication platformin accordance with one embodiment.

FIG. 6 illustrates a flowchart 600 for executing a processing action viaa group-based communication platform in accordance with one embodiment.

FIG. 7 illustrates a wireframe 700 of a group-based communicationinterface in accordance with one embodiment.

FIG. 8 illustrates a wireframe 800 of a group-based communicationinterface in accordance with one embodiment.

FIG. 9 illustrates a wireframe 900 comprising a curated list ofavailable processing actions in accordance with one embodiment.

FIG. 10 illustrates a wireframe 1000 illustrating a plurality ofprocessing actions in accordance with one embodiment.

FIG. 11 illustrates a wireframe 1100 illustrating an interactive dialogin accordance with one embodiment.

DETAILED DESCRIPTION Glossary

“Group identifier” in this context refers to one or more items of databy which a group within a group-based communication system may beidentified. Group identifiers may also be referred to as “teamidentifiers” in certain embodiments. For example, a group identifier orteam identifier may comprise ASCII text, a pointer, a memory address,and the like.

“User” in this context refers to an individual, a group of individuals,business, organization, and the like. Users may access a group-basedcommunication or messaging system using client devices. “Group-based” isused herein to refer to a system, channel, message, or virtualenvironment that has security sufficient such that it is accessible onlyto a defined group of users. The group may be defined by common accesscredentials such as those of an organization or commercial enterprise.Access may further be facilitated by a validated request to join or aninvitation to join transmitted by one group member user to anothernon-member user. Group identifiers (defined below) are used to associatedata, information, messages, etc., with specific groups.

“Sending user identifier” in this context refers to a collection ofmessages that are sent by a particular user (i.e., a client deviceassociated with the particular user). These messages may be analyzed todetermine context regarding the user (e.g., the user's expertise orinterest in a topic may be determined based on the frequency of mentionof the topic or key words associated with the topic within suchmessages).

“Contextual data” in this context may identify various aspects of aprocessing action to be performed by an external system on behalf of arequesting client device. The contextual data may be utilized by thegroup-based communication system to appropriately route a container toan appropriate proxy endpoint to trigger and external system to performa particular processing action. The contextual data may be furtherutilized by the external system to identify the requested processingaction to be performed and/or to identify any additional data thatshould be requested from the client device (e.g., via one or moreinteractive dialogs presented via a group-based user interface).Moreover, the contextual data may identify various characteristics of amessage object (e.g., a message, a file, a plurality of messages (e.g.,all messages within a communication channel), and/or the like), such asa timestamp indicating when a particular message object was shared viathe group-based communication platform, a sending-user identifierindicating a user (and/or client device) that initially shared themessage object, a client token identifying the client device requestingthe processing action, and/or the like.

“Client device” in this context refers to computer hardware(s) and/orsoftware(s) that is/are configured to access one or more services madeavailable by one or more servers. The server(s) is/are often (but notalways) on another computer system, in which case the client deviceaccesses the service by way of a network. A client device may beassociated with a group identification, where the group identificationis an electronic indication that suggests a group (e.g., user group)that the user belongs to. Client devices may include, withoutlimitation, smart phones, tablet computers, laptop computers, desktopcomputers, wearable devices, personal computers, enterprise computers,and the like.

“User profile” in this context refers to information associated with auser, including, for example, a user identifier, one or morecommunication channel identifiers (e.g., group-based communicationchannel identifiers) associated with communication channels (e.g.,group-based communication channels) that the user has been grantedaccess to, one or more group identifiers for groups with which the useris associated, an indication as to whether the user is an owner of anygroup-based communication channels, an indication as to whether the userhas any group-based communication channel restrictions, a plurality ofmessages, a plurality of emojis, a plurality of conversations, aplurality of conversation topics, an avatar, an email address, a realname (e.g., John Doe), a username (e.g., jdoe), a password, a time zone,a status, and the like. The term user profile may be usedinterchangeably with “user account, and user account details.” The useraccount details can include a subset designation of user credentials,such as, for example, login information for the user including theuser's username and password.

“Curated list” in this context refers to a listing of availableprocessing actions that may be presented to a user via a group-basedcommunication interface displayable via a client device. In certainembodiments, the curated list of processing actions excludes certainprocessing actions to the user, such that the curated list of processingactions includes only a subset of all of the processing actionsavailable to a user. For example, the curated list of processing actionsmay include a defined number of available processing actions (e.g., 5processing actions) selected based on one or more display criteria.These display criteria may be identified based at least in part oncontextual metadata associated with a message for which a processingaction is intended to be utilized (e.g., the processing actionsdisplayed within the curated list may include processing actionsavailable for messages having a particular sending user identifier, suchas messages generated by a particular app), based at least in part on acommunication channel in which a message is shared, based on recencyand/or frequency-based algorithms identify the most recently used and/ormost commonly used processing actions for a particular user, and/or thelike. In certain embodiments, the curated list may be generated based atleast in part on data stored at an individual client device (e.g., dataindicative of the most recently used processing actions for a particularclient device) and/or data stored in one or more data repositorieslocated at the group-based communication platform.

“Message distribution servers” in this context refers to computingdevices configured for interacting with various client devices forreceiving and/or disseminating messages for distribution withincommunication channels. Message distribution servers may be configuredto receive, store (in an associated database), and/or direct messagesexchanged between users (operating via client devices). Thefunctionality of the message distribution servers may be provided via asingle server or collection of servers having a common functionality, orthe functionality of the message distribution servers may be segmentedamong a plurality of servers or collections of servers performingsubsets of the described functionality of the message distributionservers. For example, a first subset of message distribution servers maybe configured for receiving messages from client devices and/or fortransmitting messages to client devices (e.g., via one or more interfaceservers). These message distribution servers may be in communicationwith a second subset of message distribution servers configured forcollecting messages distributed within communication channels and forstoring those messages within a message repository database for indexingand archiving.

“Communication channel” in this context refers to an information routeand associated circuitry that is used for data exchange between andamong systems and parts of systems. For example, a communication channelmay be established between and among various client devices, allowingthese client devices to communicate and share data between and amongeach other. These communication channels may be “group-basedcommunication channels” established between and among a select group ofclient devices (and their respective users) for sharing messages amongall users of the group. The communication channels may also and/oralternatively be one-to-one, direct message communication channelsestablished between and among two client devices (and their respectiveusers) for sharing messages among only those two users. Multiplecommunication channels may operate on each of one or more computingdevices, and therefore a communication channel identifier may beassigned to a communication channel, which indicates the physicaladdress in a database where related data of that communication channelis stored and which is utilized to identify client devices thatparticipate within the communication channel to receive data exchangedon the communication channel. The communication channel identifiertherefore ensures communication channels remain distinct and separateeven on computing devices associated with a plurality of communicationchannels. A communication channel may be “public,” which may allow anyclient device to join and participate in the information sharing throughthe communication channel. A communication channel may be “private,”which may restrict data communications in the communication channel tocertain client devices and/or users.

“Payload data” in this context refers to data forming a portion of acontainer, as discussed herein. The payload data may comprise one ormore messages (e.g., message text, files attached to an exchangedmessage, a plurality of discrete exchanged messages, and/or the like.

“Interactive dialog” in this context refers to a user interface elementconfigured to accept user input (e.g., as a selection of one or more ofa plurality of available options, as freeform input, and/or the like).The dialog may be presented as a pop-up or an overlaid display elementdisplayed visually over another portion of a user interface, or thedialog may be presented as a portion of a larger user interface element.

“External application system” in this context refers to a systemoperating via one or more servers which are in network communicationwith a group-based communication platform, and which service, manage,and/or perform actions that form various functions of an app that isaccessible via the group-based communication platform. The externalapplication systems may comprise additional storage repositories (e.g.,databases) associated with tasks, functions, and/or actions that may beperformed via the external application system. In certain embodiments,the external application system operates one or more executable softwareproducts to perform the various tasks, functions, and/or actionsassociated with the external application system. As various examples, anexternal application system may be configured for executing acalendaring/scheduling app, a to-do list app, a service provider app, asoftware testing app, a storage repository app, and/or the like.

“Data” in this context refers to data capable of being transmitted,received, and/or stored in accordance with embodiments of the presentinvention. Thus, use of any such terms should not be taken to limit thespirit and scope of embodiments of the present invention. Further, wherea computing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like. Similarly, where a computing device is describedherein to send data to another computing device, it will be appreciatedthat the data may be sent directly to another computing device or may besent indirectly via one or more intermediary computing devices, such as,for example, one or more servers, relays, routers, network accesspoints, base stations, hosts, and/or the like.

“Client token” in this context refers to an identifier that uniquelyidentifies a particular client device. The client tokens may be static(e.g., such that a client device is permanently associated with aparticular client token until an affirmative action is taken to changethe associated client token) or dynamic (e.g., such that a client tokenis assigned to a particular client device for a short duration, such asthe period of time associated with performing a particular task, theperiod of time associated with a unique client session with agroup-based communication platform, and/or the like). Moreover, clienttokens may be encrypted in certain embodiments utilizing any of avariety of encryption methodologies for added security againstunauthorized usage of the client token.

“Private group-based communication channel” in this context refers to agroup-based communication channel with restricted access such that it isnot generally accessible and/or searchable by other members of thegroup-based communication system. For example, only those users oradministrators who have knowledge of and permission to access (e.g., agroup-based communication channel identifier for the private group-basedcommunication channel is associated with their user profile after theuser has been validated/authenticated) the private group-basedcommunication channel may view content of the private group-basedcommunication channel.

“Group-based communication platform” in this context refers to acollection of computing services that are accessible to one or moreclient devices, and that are operable to provide access to a pluralityof software applications related to operations of databases. In someexamples, the group-based communication platform may take the form ofone or more central servers disposed in communication with one or moreadditional servers running software applications, and having access toone or more databases storing digital content items, application-relateddata, and/or the like. The group-based communication platform may alsosupport client retention settings and other compliance aspects. Further,the group-based communication platform may provide comprehensive thirdparty developer support that grants appropriate access to the data andallows third parties to build applications and bots to integrate withcustomer's workflows. Group-based communication platform users areorganized into organization groups (e.g., employees of each company maybe a separate organization group) and each organization group may haveone or more communication channels (e.g., group-based communicationchannels) to which users may be assigned or which the users may join(e.g., group-based communication channels may represent departments,geographic locations such as offices, product lines, user interests,topics, issues, and/or the like). A group identifier may be used tofacilitate access control for a message (e.g., access to the message,such as having the message return as part of search results in responseto a search query, may be restricted to those users having the groupidentifier associated with their user profile). The group identifier maybe used to determine context for the message (e.g., a description of thegroup, such as the name of an organization and/or a brief description ofthe organization, may be associated with the group identifier).Group-based communication system users may join and/or createcommunication channels (e.g., group-based communication channels). Somegroup-based communication channels may be globally accessible to thoseusers having a particular organizational group identifier associatedwith their user profile (i.e., users who are members of theorganization). Access to some group-based communication channels may berestricted to members of specified groups, whereby the group-basedcommunication channels are accessible to those users having a particulargroup identifier associated with their user profile. The group-basedcommunication channel identifier may be used to facilitate accesscontrol for a message (e.g., access to the message, such as having themessage return as part of search results in response to a search query,may be restricted to those users having the group-based communicationchannel identifier associated with their user profile, or who have theability to join the group-based communication channel). The group-basedcommunication channel identifier may be used to determine context forthe message (e.g., a description of the group-based communicationchannel, such as a description of a project discussed in the group-basedcommunication channel, may be associated with the group-basedcommunication channel identifier).

“Processing action” in this context refers to an executable actionperformed by an external system (e.g., an app accessible via thegroup-based communication platform). The processing action may beembodied as a data generation process, a data manipulation process,and/or the like that is perfumed based at least in part on data includedwithin a container provided from the group-based communication platformto the external system. As various examples, a processing action may bethe creation of a calendar object (e.g., via a scheduling app), thecreation of a “to-do” item (e.g., via a productivity app), the creationof a service ticket (e.g., via a service app), the creation of abookmark (e.g., via a link compilation app), the creation of a file(e.g., via a document editing app), and/or the like.

“Container” in this context refers to a collection of individual dataelements that may be transmitted between a plurality of computingentities collectively, such that the included data remains associatedtherewith. The container may be configured to store data therein with astandardized formatting, such that computing entities may be configuredto automatically determine the type of data stored within the container.For example, a container may comprise substantive data to be passedbetween computing entities stored within a payload of the container, andthe container may comprise metadata associated with the generation ofthe container that is stored within a contextual data portion of thecontainer.

“File object” in this context refers to an example of a message that maybe provided as payload data within a container to an external system toperform a requested processing action. A file object may be any of avariety of executable file types, such as a “.pdf” file, a “.docx” file,a “.xml” file, a “.html” file, a “.tp” file, and/or the like.

“Channel identifier” in this context refers to one or more items of databy which a group-based communication channel may be identified. Channelidentifiers may also be referred to as “group-based communicationchannel identifiers” in certain embodiments. For example, a group-basedcommunication channel identifier may comprise ASCII text, a pointer, amemory address, and the like.

“Message” in this context refers to any electronically generated digitalcontent object provided by a user using a client device and that isconfigured for display within a group-based communication channelinterface. Messages may also be referred to as “messagingcommunications” in certain embodiments. Messages may include or beembodied as any text, image, video, audio, files, interactive links, orcombination thereof provided by a user (using a client device). Forinstance, the user may provide a messaging communication that includestext as well as an image and a video within the messaging communicationas message contents. In such a case, the text, image, and video wouldcomprise the messaging communication or digital content object. Eachmessage sent or posted to a group-based communication channel of thegroup-based communication system includes metadata comprising thefollowing: a sending user identifier, a message identifier, messagecontents, a group identifier, and a group-based communication channelidentifier. Each of the foregoing identifiers may comprise ASCII text, apointer, a memory address, and the like

“Group-based communication channel interface” in this context refers toa virtual communications environment or feed that is configured todisplay messaging communications posted by channel members (e.g.,validated users accessing the environment using client devices) that areviewable only to the members of the group. The format of the group-basedcommunication channel interface may appear differently to differentmembers of the group-based communication channel; however, the contentof the group-based communication channel interface (i.e., messagingcommunications) will be displayed to each member of the group-basedcommunication channel. For instance, a common set of group-basedmessaging communications will be displayed to each member of therespective group-based communication channel such that the content ofthe group-based communication channel interface (i.e., messagingcommunications) will not vary per member of the group-basedcommunication channel.

“Proxy endpoint” in this context refers to a data transfer interface,for example an Application Program Interface (API) between unconnectedcomputing systems via a network. The proxy endpoint may be accessibleover the network via a URL. For example, a proxy endpoint may enabledata transfer of a container (comprising contextual data and/or payloaddata) from a group-based communication system to an external systemassociated with an app published and usable via the group-basedcommunication system. In various embodiments, the proxy endpoint isdefined at least in part by a URL accessible to the external system,wherein the URL may be utilized to direct the external system to aparticular dataset (e.g., one or more containers). As discussed herein,containers provided to the external system via the proxy endpoint maycomprise data formatted to enable usage by the external system toperform a desired processing action. The proxy endpoint enables transferof the container data to the external system while maintaining thenecessary formatting of the container to enable the external system touse the included data. Moreover, in certain embodiments the proxyendpoint enable real-time transmission of data to the external system(e.g., via push-based message transmission). In other embodiments, theproxy endpoint may be configured to enable the external system to pulldata from the group-based communication platform (e.g., upon theoccurrence of a trigger event acting to inform the external system ofthe presence of data that is ready for transmission).

DESCRIPTION

The present disclosure more fully describes various embodiments withreference to the accompanying drawings. It should be understood thatsome, but not all embodiments are shown and described herein. Indeed,the embodiments may take many different forms, and accordingly thisdisclosure should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like numbersrefer to like elements throughout.

Overview

As discussed herein, certain embodiments are directed to systems andmethods enabling a group-based communication platform to perform variousactions within external systems. Such configurations enable users of thegroup-based communication platform to initiate various actions withinvarious external systems based on commands and/or processes performedwithin a group-based communication interface of the group-basedcommunication platform. For example, messages, files, threads, groups ofmessages, and/or other objects usable within the group-basedcommunication platform may be exported from the group-basedcommunication platform and automatically imported into one or moreexternal systems to generate various objects usable within thoseexternal systems. Thus, messages exchanged via the group-basedcommunication platform may be provided to external systems to create andpopulate applicable to-do list items, to generate and populate one ormore documents, and/or the like.

The group-based communication platform is configured to provide data tothe external systems within defined containers, wherein each containercomprises contextual data indicative of the message, file, or otherobject for which the container was generated, a time-stamp associatedwith the creation of the object, a client device token identifying therequesting client device, an external system (e.g., an app) to which thecontainer is to be directed, and/or an action to be performed by theexternal system. The container further includes the object itself (e.g.,the message, file, and/or the like) within a payload portion of thecontainer to pass the object to the external system. Ultimately, thedata included within the container is passed to the external systemusing an API to provide the data to the external system in theappropriate format to execute the requested action.

Upon receipt of an appropriate request message from the external system,the group-based communication platform utilizes the client token toidentify an appropriate client device for presentation of a dialog tocollect additional information to be utilized by the external system toperform the requested action. The dialog may be retrieved from aseparate dialog storage area (e.g., stored in association with thegroup-based communication platform) accessible via a dialog API. Therequest message may, in certain embodiments, comprise a dialog triggeridentifier that may be presented to the dialog storage area via thedialog API. In return, an appropriate dialog corresponding to the dialogtrigger identifier and having appropriate fields for presentation to auser is retrieved. For example, the dialog may comprise a plurality ofalternatively selectable options (those options being available withinthe external system) for use with the requested action. Various datagenerated and/or otherwise provided via the dialog are provided back tothe external system and associated with the original container presentedthereto. Upon successfully providing data to the external system, thegroup-based communication platform provides a confirmation to the clientdevice (e.g., as a separate notification icon and/or via a messageprovided via the group-based communication interface).

Example System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a network device, such as a server orother network entity, configured to communicate with one or moredevices, such as one or more client devices. In some preferred andnon-limiting embodiments, the computing device may include fixedcomputing devices, such as a personal computer or a computerworkstation. Still further, example embodiments may be embodied by anyof a variety of mobile devices, such as a portable digital assistant(PDA), mobile phone, smartphone, laptop computer, tablet computer,wearable device, or any combination of the aforementioned devices.

FIG. 1 illustrates an example computing system 100 within whichembodiments of the present invention may operate. Users may access agroup-based communication platform 118 via a communication network 108using client devices 102-106.

Communication network 108 may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, communication network 108 mayinclude a cellular telephone, an 802.11, 802.16, 802.20, and/or WiMaxnetwork. Further, the communication network 108 may include a publicnetwork, such as the Internet, a private network, such as an intranet,or combinations thereof, and may utilize a variety of networkingprotocols now available or later developed including, but not limited toTCP/IP based networking protocols. As discussed herein, the networkingprotocol is configured to enable data transmission via websocketcommunications. For instance, the networking protocol may be customizedto suit the needs of the group-based communication system. In someembodiments, the protocol is a custom protocol of JSON objects sent viaa websocket channel. In some embodiments, data may be transmitted via aplurality of protocols, such as JSON over RPC, JSON over REST/HTTP, andthe like.

In the illustrated embodiment, the group-based communication platform118 includes an at least one message distribution server(s) 110accessible via the communication network 108. Collectively, the at leastone message distribution server(s) 110 is configured for receivingmessages transmitted from one or more client devices 102-106, storingthe messages within database storage areas for individual communicationchannels, and/or for transmitting messages to appropriate client devices102-106.

The client devices 102-106 may be any computing device as defined above.Electronic message data exchanged between the message distributionserver(s) 110 and the client device 102-106 may be provided in variousforms and via various methods.

In some preferred and non-limiting embodiments, one or more of theclient devices 102-106 are mobile devices, such as smartphones ortablets. The one or more client devices may execute an “app” to interactwith the message distribution server(s) 110. Such apps are typicallydesigned to execute on mobile devices, such as smartphones or tablets.For example, an app may be provided that executes on mobile deviceoperating systems such as Apple Inc.'s iOS®, Google Inc.'s Android®, orMicrosoft Inc.'s Windows 10 Mobile®. These platforms typically provideframeworks that allow apps to communicate with one another, and withparticular hardware and software components of mobile devices. Forexample, the mobile operating systems named above each providesframeworks for interacting with location services circuitry, wired andwireless network interfaces, user contacts, and other applications.Communication with hardware and software modules executing outside ofthe app is typically provided via application programming interfaces(APIs) provided by the mobile device operating system. Thus, via the appexecuting on the client devices 102-106, these client devices 102-106are configured for communicating with the group-based communicationplatform 118.

In some preferred and non-limiting embodiments, the client devices102-106 may interact with the message distribution server(s) 110 via aweb browser. The client devices 102-106 may also include varioushardware or firmware designed to interact with the message distributionserver(s) 110. Again, via the browser of the client devices 102-106, theclient devices 102-106 are configured for communicating with thegroup-based communication platform 118.

In some embodiments of an exemplary group-based communication platform118, a message or messaging communication may be sent from a clientdevice 102-106 to a group-based communication platform 118. In variousimplementations, messages may be sent to the group-based communicationplatform 118 over communication network 108 directly by one of theclient devices 102-106. The messages may be sent to the group-basedcommunication platform 118 via an intermediary such as a message server,and/or the like. For example, a client device 102-106 may be a desktop,a laptop, a tablet, a smartphone, and/or the like that is executing aclient application (e.g., a group-based communication app). In oneimplementation, the message may include data such as a messageidentifier, sending user identifier, a group identifier, a group-basedcommunication channel identifier, message contents (e.g., text, emojis,images, links), attachments (e.g., file objects), message hierarchy data(e.g., the message may be a reply to another message), third partymetadata, and/or the like. In one embodiment, the client device 102-106may provide the following example message, substantially in the form ofa (Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST messageincluding eXtensible Markup Language (“XML”) formatted data, as providedbelow:

POST /authrequest.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <auth_request>     <timestamp>2020-12-31 23:59:59</timestamp>    <user_accounts_details>         <user_account_credentials>            <user_name>ID_user_1</user_name>            <password>abc123</password>             //OPTIONAL<cookie>cookieID</cookie>             //OPTIONAL<digital_cert_link>www.mydigitalcertificate.com/    JohnDoeDaDoeDoe@gmail.com/mycertifcate.dc</digital_cert_link>            //OPTIONAL <digital_certificate>_DATA_</digital_certificate>        </user_account_credentials>     </user_accounts_details>    <client_details> //iOS Client with App and Webkit             //itshould be noted that although several client details            //sections are provided to show example variants of client            //sources, further messages will include only on to save            //space         <client_IP>10.0.0.123</client_IP>        <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 likeMac OS X)     AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0Mobile/11D201     Safari/9537.53</user_agent_string>        <client_product_type>iPhone6,1</client_product_type>        <client_serial_number>DNXXX1X1XXXX</client_serial_number>        <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>        <client_OS>iOS</client_OS>        <client_OS_version>7.1.1</client_OS_version >        <client_app_type>app with webkit</client_app_type>        <app_installed_flag>true</app_installed_flag>        <app_name>MSM.app</app_name>         <app_version>1.0</app_version>         <app_webkit_name>MobileSafari</client_webkit_name>        <client_version>537.51.2</client_version>     </client_details>    <client_details> //iOS Client with Webbrowser        <client_IP>10.0.0.123</client_IP>        <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 likeMac OS X)     AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0Mobile/11D201     Safari/9537.53</user_agent_string>        <client_product_type>iPhone6,1</client_product_type>        <client_serial_number>DNXXX1X1XXXX</client_serial_number>        <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>        <client_OS>iOS</client_OS>        <client_OS_version>7.1.1</client_OS_version >        <client_app_type>web browser</client_app_type>        <client_name>Mobile Safari</client_name>        <client_version>9537.53</client_version>     </client_details>    <client_details> //Android Client with Webbrowser        <client_IP>10.0.0.123</client_IP>        <user_agent_string>Mozilla/5.0 (Linux; U; Android 4.0.4; en-us;Nexus S Build/IMM76D)     AppleWebKit/534.30 (KHTML, like Gecko)Version/4.0 Mobile Safari/534.30</user_agent_string>        <client_product_type>Nexus S</client_product_type>        <client_serial_number>YXXXXXXXXZ</client_serial_number>        <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXX</client_UDID>        <client_OS>Android</client_OS>        <client_OS_version>4.0.4</client_OS_version>        <client_app_type>web browser</client_app_type>        <client_name>Mobile Safari</client_name>        <client_version>534.30</client_version>     </client_details>    <client_details> //Mac Desktop with Webbrowser        <client_IP>10.0.0.123</client_IP>        <user_agent_string>Mozilla/5.0 (Macintosh; Intel Mac OS X10_9_3) AppleWebKit/537.75.14     (KHTML, like Gecko) Version/7.0.3Safari/537.75.14</user_agent_string>        <client_product_type>MacPro5,1</client_product_type>        <client_serial_number>YXXXXXXXXZ</client_serial_number>        <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXX</client_UDID>        <client_OS>Mac OS X</client_OS>        <client_OS_version>10.9.3</client_OS_version>        <client_app_type>web browser</client_app_type>        <client_name>Mobile Safari</client_name>        <client_version>537.75.14</client_version>     </client_details>    <message>        <message_identifier>ID_message_10</message_identifier>        <team_identifier>ID_team_1</team_identifier>        <channel_identifier>ID_channel_1</channel_identifier>        <contents>That is an interesting invention. I have attached acopy our patent policy.</contents>        <attachments>patent_policy.pdf</attachments>     </message></auth_request>

In the illustrated embodiment, the group-based communication platform118 comprises a plurality of message distribution server(s) 110configured to receive messages transmitted between a plurality of clientdevices 102-106 within a channel identified by a channel identifierand/or a group identifier, and to facilitate dissemination of thosemessages among client devices 102-106 that collectively form themembership of the communication channel.

In some embodiments, data indicating responses may be associated withthe message. For example, responses to the message by other users mayinclude reactions (e.g., selection of an emoji associated with themessage, selection of a “like” button associated with the message),clicking on a hyperlink embedded in the message, replying to the message(e.g., posting a message to the group-based communication channelinterface in response to the message), downloading a file associatedwith the message, sharing the message from one group-based communicationchannel to another group-based communication channel, pinning themessage, starring the message, and/or the like. In one implementation,data regarding responses to the message by other users may be includedwith the message, and the message may be parsed (e.g., using PHPcommands) to determine the responses. In another implementation, dataregarding responses to the message may be retrieved from a database. Forexample, data regarding responses to the message may be retrieved via aMySQL database command similar to the following:

SELECT messageResponses

FROM MSM_Message

WHERE messageID=ID_message_10.

For example, data regarding responses to the message may be used todetermine context for the message (e.g., a social score for the messagefrom the perspective of some user). In another example, data regardingresponses to the message may be analyzed to determine context regardingthe user (e.g., the user's expertise in a topic may be determined basedon the responses to the user's message regarding the topic).

In embodiments, attachments may be included with the message. If thereare attachments, file objects may be associated with the message. In oneimplementation, the message may be parsed (e.g., using PHP commands) todetermine file names of the attachments. For example, file contents maybe analyzed to determine context for the message (e.g., a patent policydocument may indicate that the message is associated with the topic“patents”).

In embodiments, third party metadata may be associated with the message.For example, third party metadata may provide additional contextregarding the message or the user that is specific to a company, group,group-based communication channel, and/or the like. In oneimplementation, the message may be parsed (e.g., using PHP commands) todetermine third party metadata. For example, third party metadata mayindicate whether the user who sent the message is an authorizedrepresentative of the group-based communication channel (e.g., anauthorized representative may be authorized by the company to respond toquestions in the group-based communication channel).

In embodiments, a conversation primitive may be associated with themessage. In one implementation, a conversation primitive is an elementused to analyze, index, store, and/or the like messages. For example,the message may be analyzed by itself, and may form its own conversationprimitive. In another example, the message may be analyzed along withother messages that make up a conversation, and the messages that makeup the conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as themessage, a specified number (e.g., two) of preceding messages and aspecified number (e.g., two) of following messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the message and other messages (e.g., inthe channel) and/or proximity (e.g., message send order proximity,message send time proximity) of these messages.

In embodiments, various metadata, determined as described above, and/orthe contents of the message may be used to index the message (e.g.,using the conversation primitive) and/or to facilitate various facets ofsearching (i.e., search queries that return results from the messagedistribution servers 107). Metadata associated with the message may bedetermined and the message may be indexed in the message distributionserver(s) 110. In one embodiment, the message may be indexed such that acompany's or a group's messages are indexed separately (e.g., in aseparate index associated with the group and/or company that is notshared with other groups and/or companies). In one implementation,messages may be indexed at a separate distributed repository (e.g., tofacilitate data isolation for security purposes). If there areattachments associated with the message, file contents of the associatedfiles may be used to index such files in the message distributionserver(s) 110 to facilitate searching. In one embodiment, the files maybe indexed such that a company's or a group's files are indexed at aseparate distributed repository. Similarly, as discussed herein, appdata associated with various external application systems and/orprocessing actions may be stored in association with a particulargroup's messages, such that app data associated with a plurality ofgroups are stored separately.

Examples of electronic message exchange among one or more client devices102-106 and the group-based communication platform 118 are describedbelow in reference to FIG. 1.

As shown in FIG. 1, the group-based communication platform 118 enablesindividual client devices 102-106 to exchange messages with one anotherand to interact with one or more external application systems 112-116.To exchange messages between client devices 102-106, individual clientdevices 102-106 transmit messages (e.g., text-based messages, fileobjects, video and/or audio streams, and/or the like) to the group-basedcommunication platform 118. Those messages are ultimately provided toone or more message distribution server(s) 110, which indexes themessages and distributes those messages to the intended recipients(e.g., client devices 102-106) of the message.

In accordance with the embodiment shown in FIG. 1, the client devices102-106 are configured to display the received messages in acontextually-relevant user interface available to the user of the clientdevice. For example, messages transmitted from a first client device 102as a part of a group-based communication channel are displayed in a userinterface display on client devices 102-106 associated with othermembers of the group-based communication channel.

As discussed in greater detail herein, messages may be provided toexternal application systems 112-116 to initiate one or more processingactions executable within the respective external application system. Incertain embodiments, those processing actions are made available toclient devices 102-106 on a group-basis (e.g., such that individualprocessing actions are available to every member of a particular group),on a communication channel basis (e.g., such that individual processingactions are available to every member of a particular communicationchannel), on an individual basis (e.g., such that individual processingactions are available to certain individual client devices 102-106), ona sending user identifier basis (e.g., such that individual processingactions are available only for certain messages transmitted byparticular users, such that the message is associated with a particularsending user identifier, and/or the like. As an added limitation,certain processing actions may only be executable via client devices102-106 that are directly authenticated with a particular externalapplication system configured to execute the processing action (asindicated by the dashed lines between the individual client devices102-106 and example external application system 112.

Example Apparatuses Utilized with Various Embodiments

Each message distribution server(s) 110 may be embodied by one or morecomputing systems, such as apparatus 200 shown in FIG. 2. The apparatus200 may include processor 202, memory 204, input/output circuitry 206,communications communication circuitry 208, and message amplifiercircuitry 210. The apparatus 200 may be configured to execute theoperations described herein with respect to FIG. 3-FIG. 11. Althoughthese components 202-210 are described with respect to functionallimitations, it should be understood that the particular implementationsnecessarily include the use of particular hardware. It should also beunderstood that certain of these components 202-210 may include similaror common hardware. For example, two sets of circuitries may bothleverage use of the same processor, network interface, storage medium,or the like to perform their associated functions, such that duplicatehardware is not required for each set of circuitries.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 204 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus 200 to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 202 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 202 may beconfigured to execute instructions stored in the memory 204 or otherwiseaccessible to the processor 202. In some preferred and non-limitingembodiments, the processor 202 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 202 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 202 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 202 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

As just one example, the processor 202 may be configured to maintain oneor more communication channels connecting a plurality of client devices102-106 to enable message sharing therebetween. The processor 202ensures that messages intended for exchange between the client devices102-106 within the particular communication channel are properlydisseminated to those client devices 102-106 for display withinrespective display windows provided via the client devices 102-106.

Moreover, the processor 202 may be configured to synchronize messagesexchanged on a particular communication channel with a database forstorage and/or indexing of messages therein. In certain embodiments, theprocessor 202 may provide stored and/or indexed messages fordissemination to client devices 102-106.

In some embodiments, the apparatus 200 may include input/outputcircuitry 206 that may, in turn, be in communication with processor 202to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 206 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 206 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms. The processorand/or user interface circuitry comprising the processor may beconfigured to control one or more functions of one or more userinterface elements through computer program instructions (e.g., softwareand/or firmware) stored on a memory accessible to the processor (e.g.,memory 204, and/or the like).

The communication circuitry 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communication circuitry 208may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communication circuitry 208 may include one or more networkinterface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communication circuitry 208 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

Message amplifier circuitry 210 includes hardware configured to copy andamplify electronic messages and associated metadata received from one ormore client devices 102-106 to other client devices 102-106 based ondatabase shard(s). The message amplifier circuitry 210 may utilizeprocessing circuitry, such as the processor 202, to perform theseactions. However, it should also be appreciated that, in someembodiments, the message amplifier circuitry 210 may include a separateprocessor, specially configured Field Programmable Gate Array (FPGA), orApplication Specific Integrated Circuit (ASIC) for performing thefunctions described herein. The message amplifier circuitry 210 may beimplemented using hardware components of the apparatus 200 configured byeither hardware or software for implementing these planned functions.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 200. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

The term “circuitry” should be understood broadly to include hardwareand, in some embodiments, software for configuring the hardware. Withrespect to components of each apparatus 200, the term “circuitry” asused herein should therefore be understood to include particularhardware configured to perform the functions associated with theparticular circuitry as described herein. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, input/output devices, and the like. In someembodiments, other elements of the apparatus 200 may provide orsupplement the functionality of particular circuitry. For example, theprocessor 202 may provide processing functionality, the memory 204 mayprovide storage functionality, the communication circuitry 208 mayprovide network interface functionality, and the like.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present invention may be configured as methods,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions (e.g., computer software) embodied in the storagemedium. Any suitable computer-readable storage medium may be utilizedincluding non-transitory hard disks, CD-ROMs, flash memory, opticalstorage devices, or magnetic storage devices.

Moreover, although not shown, various embodiments of a group-basedcommunication platform may comprise one or more databases configured forstoring and/or indexing messages exchanged within various group-basedcommunication channels.

Example Data Flows

FIG. 3 provides a flowchart 300 illustrating various processes formaking various processing actions available to one or more clientdevices 102-106. In certain embodiments, processing actions may be madeavailable to the group-based communication platform 118 for usage byusers via associated client devices 102-106. In various embodiments,processing actions may be published to the group-based communicationplatform 118 such that any client device accessing the group-basedcommunication platform 118 may have access to the various processingactions. In other embodiments, the processing actions may be madeavailable to particular groups having access to additionalfunctionalities provided via the external application system 112-116associated with the particular processing action. In such embodiments,underlying configuration data for a particular processing action isstored in a database shard(s) associated with a particular group, andthe underlying configuration data thereby makes the particularprocessing action available to any client device associated with theparticular database shard(s).

Beginning at block 302, the group-based communication platform 118receives app data from an external application system 112-116 comprisingprocessing action data. The app data may comprise data indicative ofvarious objects (e.g., file objects) that may be provided from anexternal application system 112-116 to the group-based communicationplatform 118, as well as various processing actions that may beperformed at the external application system 112-116 based on data(e.g., contextual data and/or payload data within a container) providedfrom the group-based communication platform 118 to the externalapplication system 112-116. As discussed in reference to FIG. 4 and FIG.5, portions of the app data associated with a particular processingaction may comprise data identifying a particular proxy endpoint to beutilized for data transfer between the group-based communicationplatform 118 and the associated external application system 112-116, theapp data associated with the particular processing action mayadditionally comprise data identifying one or more identifiers (e.g., aname to be displayed to users and/or a callback identifier to beutilized via executable programs to initiate the processing action)associated with the processing action, a description associated with theprocessing action, an image (e.g., an icon) associated with theprocessing action, and/or the like.

With reference again to FIG. 3, the process for making a particularprocessing action available continues as indicated at block 304, bystoring app data in database shards corresponding to particular groups.As discussed herein, the app data may be stored individually for variousgroups, and accordingly the app data is stored in a database shardassociated with the particular group, such that client devices 102-106associated with the particular group have access to the stored app data(and accordingly the app data associated with the particular processingaction). Thus, when providing updates to functionality provided by theexternal application system 112-116, updates are disseminated and storedvia each database shard(s) such that the updated app data is availableto individual groups. In certain embodiments, updates may bedisseminated to individual database shards only upon approval from anadministrator associated with the particular group and database shard.Similarly, when introducing a new processing action, app data associatedwith the new processing action is disseminated to all database shard(s)having app data associated with the particular external applicationsystem 112-116.

Making a particular processing action available to client devices102-106 associated with a particular group continues as indicated atblock 306 of FIG. 3. As illustrated therein, the group-basedcommunication platform 118 identifies one or more processing actionsdefined within the app data provided by a particular externalapplication system 112-116. In certain embodiments, the app data may beprovided from an external application system 112-116 specifically inreference to a particular processing action (e.g., provided as an updateto an existing app), although the app data may also generally beprovided as data defining various functionalities available via the app,and the processing actions may be identified as one of the plurality offunctionalities therein. The identified processing actions may beutilized to populate an actions table identifying one or more processingactions available to client devices 102-106 associated with a particulargroup. In certain embodiments, a plurality of actions tables may bestored within each database shard, with each action table correspondingto a particular external application system 112-116. For example, afirst action table may identify processing actions available from afirst external application system 112, and a second actions table mayidentify processing actions available from a second external applicationsystem 114. As yet another example, a single actions table may beprovided in each database shard, wherein the single actions tableidentifies all processing actions available to client devices 102-106associated with the particular group, including processing actionsavailable from a plurality of external application systems 112-116.

In certain embodiments, the action table identifies variouscharacteristics of each processing action identified therein. Forexample, the actions table identifies instances in which particularprocessing actions are to be presented to client devices 102-106,particular messages eligible for usage with a particular processingaction, particular users eligible to use particular processing actions,and/or the like.

Finally, as indicated at block 310 of FIG. 3, the group-basedcommunication platform 118 provides data indicative of processingactions available to particular client devices 102-106, to clientdevices 102-106 upon receipt of requests from the individual clientdevices 102-106. For example, a client device 102-106 may receive userinput selecting a particular selection element 704 (as illustrated inFIG. 7, discussed in greater detail herein), and may transmit a requestfor a curated list of available processing actions to the group-basedcommunication platform 118. As discussed in greater detail in referenceto FIG. 6-FIG. 11, the group-based communication platform 118 provides acurated list of at least a subset of available processing actions(processing actions defined within the actions table) to be displayedvia a user interface element via the client device.

In certain embodiments, the actions table may remain stored at thegroup-based communication platform 118 (e.g., via database shards), andmay be selectably accessible by the client devices 102-106 viacommunication network 108. However, in certain embodiments, at least aportion of the actions table (e.g., portions of the actions tableutilized to populate a curated list) may be stored locally on a clientdevice 102-106 (e.g., via a cache memory populated upon startup of agroup-based communication app on the client device 102-106).

Moreover, updates may be provided to the actions table (or processingactions indicated within the actions table) from the respective externalapplication systems 112-116. In certain embodiments, updates toindividual processing actions may be provided from the applicableexternal application system 112-116 individually, or updates toprocessing actions may be provided from applicable external applicationsystems 112-116 as a group, such that a single transmission of updatedata may be provided from a particular external application system112-116 to provide updates for a plurality of processing actionsassociated with that external application system 112-116 simultaneously.

FIG. 4 illustrates a wireframe 400 of a developer user interfacepresented to a developer (e.g., via a client device 102-106 usable bythe developer) enabling usage of a particular processing action. Asshown in FIG. 4, the developer user interface is configured to receiveuser input specifying a request URL relating to the external applicationsystem 112-116 for a particular processing action. The URL identifiesthe location to which any data (e.g., contextual data and/or payloaddata included within a container, additional data provided from a clientdevice 102-106 in response to an interactive dialog, and/or the like) isprovided to the external application system 112-116 to enable theexternal application system 112-116 to identify the requested processingaction and to execute the requested processing action. Moreover, thedeveloper user interface is additionally configured to receive userinput (e.g., via a client device 102-106) initiating a process formaking a particular processing action available to users of thegroup-based communication platform 118 (as discussed in reference to theflowchart 300 of FIG. 3, herein). Specifically, as shown in the examplewireframe 400 of FIG. 4, the user interface includes an interactive“Create New Action” interface element that may be selected to initiatethe process for providing relevant data to the group-based communicationplatform 118, for example, via the wireframe 500 illustrated in FIG. 5and discussed herein.

Moreover, as shown in FIG. 4, the group-based communication platform 118is configured to receive additional data regarding dynamic content to bepresented to client devices 102-106. Such dynamic content may beexternal application system specific, and may be utilized to direct data(e.g., payload data) for a particular usage within the externalapplication system 112-116. For example, the dynamic data may identifyvarious existing data within the external application system 112-116,such that the external application system 112-116 may appropriatelydirect content of the container to the appropriate usage therein.

As mentioned above in reference to FIG. 4, the wireframe 500 shown inFIG. 5 provides a secondary developer user interface configured toreceive additional data regarding the functionality of a processingaction to be made available to users of the group-based communicationplatform 118 (e.g., client devices 102-106 associated with a particulargroup). As discussed in reference to the flowchart 300 of FIG. 3, theprocessing action-specific data of certain embodiments comprises aprocessing action name and description to be presented to client devices102-106 (e.g., via appropriate user interfaces), an icon or other imageto be associated with the processing action, and a callback ID that maybe included with containers to identify the relevant processing actionto be utilized with the data included in the container. In certainembodiments, the executable portions of the processing action are storedlocally at the relevant external application system, such that thegroup-based communication platform 118 provides relevant data in anappropriate format (e.g., via an API providing data via the URLspecified during setup of the processing action) to the externalapplication system, and provides various interactive dialogs and/orother messages relevant to the processing action to a requesting clientdevice 102-106.

FIG. 6 illustrates a flowchart 600 providing example steps involved ininitiating/executing a processing action according to one embodiment. Asshown therein, the process for initiating a processing action beginsupon receipt of a request for a processing action for a particularmessage, as shown at block 602. Upon receipt of the request, thegroup-based communication platform 118 generates and provides a curatedlist of available processing actions to the requesting client device102-106 (e.g., as displayed in curated list 804 or curated list 902 ofFIG. 8 and FIG. 9, discussed herein), as shown at block 604. In certainembodiments, the initial request may be generated at the client device102-106 upon selection of a selection element 704 (as shown in FIG. 7)and/or a processing action option 706 displayed upon interacting withthe selection element 704. As discussed herein, the selection element704 may be message specific, such that interacting with the selectionelement 704 for a particular message (e.g., a text-based message 702, afile object, a plurality of text-based messages and/or file objectsshared within a communication channel, and/or the like) and selecting aprocessing action causes the processing action to be performed for themessage for which the processing action is selected.

As shown in the figures, the curated list of available processingactions may comprise a list of a defined number of available processingactions to be displayed at a client device 102-106. The number ofprocessing actions to be included in the curated list, may be identifiedbased on characteristics of the message for which the processing actionis to be initiated (e.g., the sending user identifier associated withthe message, content of the message itself, the communication channel inwhich the message was shared, and/or the like), characteristics of therequesting client device 102-106 (e.g., whether the client device102-106 is a mobile device, a desktop device, and/or the like), and/orthe like.

Moreover, the content of the curated list (e.g., the processing actionsto be included in the curated list), as well as the order in whichprocessing actions are displayed within the curated list may beidentified based at least in part on characteristics of the message(e.g., the sending user identifier, the channel identifier associatedwith the message, and/or the like), data indicative of user preferencesstored at the individual client devices 102-106, data indicative ofhistorical processing action usage by the client device 102-106 (e.g.,indicative of most recently utilized processing actions and/or mostcommonly utilized processing actions). The group-based communicationplatform 118 may utilize one or more algorithms (e.g., machine-learningalgorithms) to generate an appropriate ordering for display of thecurated list of available processing actions via the client device102-106.

As shown at block 606, the group-based communication platform 118receives a selection of a particular processing action to be initiatedfor a particular message. The requesting client device 102-106 providesdata identifying the requested processing action upon receipt ofcorresponding user input to the group-based communication platform 118.In certain embodiments, the selected processing action may be selectedfrom the curated list, although the processing action may also beselected within a search interface that may be utilized to navigate allavailable processing actions as indicated within an actions table asdiscussed herein.

As shown at block 608, the group-based communication platform 118performs a validation check to determine whether the selected processingaction is available for use. Although illustrated as occurring afterselection of a particular processing action for execution, it should beunderstood that the validation check described with respect to block 608may be performed at any time. For example, the validation check may beperformed prior to generating the curated list to be provided to therequesting client device 102-106. For example, the validation check maydetermine whether the particular processing action has an associated URLfor transmission of relevant data, whether the particular processingaction is reflected within other app data provided from the externalapplication system, and/or the like. Upon determining that theprocessing action is unavailable, the process for executing theprocessing action may stop, and an error message may be displayed viathe client device 102-106. In certain embodiments, the processing actionmay subsequently be removed from the actions table such that theprocessing action is thereafter indicated as unavailable for subsequentrequests.

Moreover, although not shown in FIG. 6, the group-based communicationplatform 118 and/or the external application system 112-116 associatedwith a requested processing action may perform an authentication checkto determine whether the requesting client device has an associatedaccount and/or other user login with the external application system112-116. For example, the external application system 112-116 mayprovide user specific features, and accordingly the client device mustbe authenticated with the external application system 112-116 to providesuch features. In various embodiments, authentication may be providedvia the group-based communication platform 118 to enable the externalapplication system 112-116 to associate requests to execute processingactions provided through the group-based communication platform 118 withan existing user account (and associated user-specific functionality)stored at the external application system 112-116. Authentication viathe group-based communication platform 118 may be performed via aninteractive dialog provided to the client device 102-106 and configuredto receive user input of a user identifier and/or password for anaccount stored at the external application system 112-116. The datareceived via the authentication process may be passed to the externalapplication system 112-116 as a part of a container (discussed ingreater detail herein) thereby enabling the external application system112-116 to associate the authenticated user account stored at theexternal application system 112-116 with a client identifier (e.g., aclient token) provided with the container.

Upon determining that the selected processing action is available, thegroup-based communication platform 118 generates a container comprisingcontextual data and payload data for the requested processing action, asindicated at block 610. As discussed herein, the container comprisescontextual data identifying data usable by the external applicationsystem to identify the requested processing action, to identify theclient device requesting the processing action, and/or identifying themessage on which the processing action is to be performed. As a specificexample, the group-based communication platform 118 assembles thecontextual data for the container to comprise (1) one or moreverification tokens (e.g., a group-based communication platform 118verification token), (2) a group-identifier, (3) a channel identifier,(4) a user identifier (e.g., a client device 102-106 specific clienttoken identifying the client device 102-106 that requests the particularprocessing action), (5) a processing action identifier (e.g., aprocessing action name, and/or other identifying string), (6) an actiontype defining a processing action type, (7) a trigger defining aninteractive dialog to be presented to the client device 102-106 inresponse to initialization of the processing action, (8) a response URLenabling the external application system to transmit a response (e.g., aconfirmation response) back to the requesting client device 102-106, (9)a timestamp indicating when the processing action is requested, and/orthe like. The container additionally comprises payload data comprisingthe message for which the processing action was requested.

Upon generation of the container, the group-based communication platform118 provides the container to the external application system 112-116identified with the contextual data via the proxy endpoint identifiedwithin the contextual data, as shown at block 612. The proxy endpointprovides an API for passing the container from the group-basedcommunication platform 118 to the external application system 112-116,thereby enabling the external application system 112-116 to consume thecontextual data and/or the payload data within the container whileexecuting a requested processing action. Providing the container to theexternal application system 112-116 causes the external applicationsystem 112-116 to initiate the requested processing action as identifiedin the contextual data, as shown at block 614.

As discussed herein, the processing action may cause the externalapplication system 112-116 to generate a new data object to be storedwithin a data repository associated with the external application system112-116, to modify an existing data object stored within the datarepository associated with the external application system 112-116, todelete an existing data object stored within the data repositoryassociated with the external application system 112-116, and/or thelike. For example, the external application system 112-116 may execute acalendar app, and therefore the processing action may be configured togenerate a new calendar entry to be stored within the data repositoryassociated with the external application system 112-116. As yet anotherexample, the external application system 112-116 may be embodied as asoftware bug tracking system, and therefore the processing action mayedit an existing record associated with a particular software bug withadditional information as identified within a particular message sharedwithin the group-based communication platform 118.

As a part of executing the processing action, the external applicationsystem 112-116 provides a response to the group-based communicationplatform 118 which causes the group-based communication platform 118 toprovide an interactive dialog to the requesting client device, asindicated at block 616 and block 618. FIG. 11, discussed in greaterdetail herein, provides an example interactive dialog 1102 presented viaa user interface displayed on the client device 102-106 to requestadditional data to be utilized while executing the processing action. Incertain embodiments, the interactive dialog may request data indicativeof a particular data object stored within the data repository associatedwith the external application system 112-116 to be edited based onexecution of the processing action, as indicated at block 620 of FIG. 6.The interactive dialog may additionally be configured to receiveadditional data (e.g., text-based data, images, and/or the like) asadditional comments to be provided with the payload data to the externalapplication system, as indicated at block 622 of FIG. 6.

The group-based communication platform 118 may additionally beconfigured for interpreting one or more error states that may beencountered as a result of passing the container to the externalapplication system 112-116. For example, if the group-basedcommunication platform 118 does not receive a response from the externalapplication system 112-116 within a defined period of time (e.g., 5seconds after transmitting the container via the proxy endpoint), thegroup-based communication platform 118 may provide an error message(e.g., in the form of an icon, a dialog, or a message displayed withinthe communication interface). As yet another example, upon receipt of aresponse from the external application system 112-116 indicating anerror occurred, the group-based communication platform 118 may beconfigured to communicate the received error response to the requestingclient device 102-106. While the group-based communication platform 118awaits the receipt of the response, the client device 102-106 maymaintain an open dialog indicative of the requested processing action,such that any errors received and passed on to the client device 102-106may be easily correlated with the recently requested processing action.

Once the external application system 112-116 completes execution of therequested processing action, the external application system 112-116provides a confirmation response to the group-based communicationplatform 118, as indicated at block 624, and the group-basedcommunication platform 118 provides a confirmation message to therequesting client device, as indicated at block 626. In certainembodiments, the confirmation message may be displayed via a dialogdisplayed via the user interface of the requesting client device 102-106or the confirmation message may be displayed as a message exchanged viathe group-based communication platform 118. In certain embodiments, theconfirmation message may be displayed within the same communicationchannel in which the message of the payload data was originally shared(e.g., the confirmation message may be shared publicly to be visible toall client devices 102-106 having access to the particular communicationchannel, or the confirmation message may be shared privately, to bevisible only to the requesting client device 102-106). The confirmationmessage may alternatively be provided to the requesting client device102-106 via a separate communication channel operable between therequesting client device 102-106 and the external application system112-116 (e.g., operating an app that provides messages to the clientdevice 102-106).

FIG. 7 is an example wireframe 700 providing a group-based communicationinterface as visible via a client device 102-106. The example shown inFIG. 7 illustrates messages shared between various client devices102-106 within the “#general” communication channel. As shown in FIG. 7,a selection element 704 has been selected for text-based message 702,thereby providing a visible menu of action items that may be performedwith respect to the selected text-based message 702. One of thosedisplayed options is a processing action option 706, which causes theuser interface to display options (e.g., a curated list 804, as shown inFIG. 8) of available processing actions that may be performed for theselected text-based message 702.

FIG. 8 provides another example wireframe 800 providing a group-basedcommunication interface as visible via a client device 102-106. Theexample shown in FIG. 8 illustrates messages shared between variousclient devices 102-106 within the “#random” communication channel. Asshown in FIG. 8, a selection element (not shown) has been selected for atext-based message 802, causing a visible menu of action items to bedisplayed that may be performed for the selected text-based message 802.As a part of the visible menu, a curated list 804 of availableprocessing actions is displayed, along with an option for reviewingadditional available processing actions by selecting the “More MessageActions” item.

FIG. 9 provides yet another example wireframe 900 of a user interfacethat may be provided with a group-based communication interface,particularly as it may be provided via a mobile device. The exampleshown in FIG. 9 illustrates a visible menu of action items that may bedisplayed via a client device 102-106 upon receipt of user inputselecting a particular message. As shown in FIG. 9, the visible menucomprises a curated list 902 of available processing actions, along withan option for reviewing additional available processing actions byselecting the “More Message Actions” item.

FIG. 10 provides another example wireframe 1000 of a user interface thatmay be provided with a group-based communication interface, particularlyas it may be presented via a mobile device. The example shown in FIG. 10provides an example menu that may be displayed upon a user selecting a“More Message Actions” item as shown in FIG. 9, discussed above. Thewireframe 1000 of FIG. 10 comprises a search functionality configuredfor receipt of user input searching for a particular processing action.The wireframe 1000 additionally comprises a complete list of availableprocessing actions for the selected message. As discussed herein, theprocessing actions identified within the listing shown in wireframe 1000are identified from an actions table stored within a data repositoryassociated with the group-based communication platform 118 andidentifying processing actions available for a particular group,channel, message, client device, and/or the like.

FIG. 11 is a wireframe 1100 illustrating an example interactive dialog1102 displayable via a client device 102-106 after requesting aprocessing action to be executed. As shown in FIG. 11, the interactivedialog 1102 is configured to receive data indicating a particular story(e.g., data object) that the payload data of the container should beassociated. Moreover, the interactive dialog 1102 may be configured toreceive additional comments that may be associated with the payload dataof the container and utilized by the external application system toexecute the requested processing action.

CONCLUSION

Many modifications and other embodiments will come to mind to oneskilled in the art to which this disclosure pertains having the benefitof the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that thedisclosure is not to be limited to the specific embodiments disclosedand that modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although specific terms areemployed herein, they are used in a generic and descriptive sense onlyand not for purposes of limitation.

What is claimed is:
 1. A system configured for initiating a processingaction within an external application system based at least in part on afile object shared via a group-based communication platform, wherein thegroup-based communication platform comprises: one or more non-transitorymemory storage repositories, wherein the one or more non-transitorymemory storage repositories comprise a processing action tableidentifying one or more processing actions available for one or morefile objects; and one or more processors, wherein the one or moreprocessors are collectively configured to: receive, from a clientdevice, a selection of a file object and a processing action to beperformed by an external application system for a selected file object,wherein a selected processing action is selected from the processingaction table; provide, to the external application system, payload dataidentifying the selected file object and contextual data identifying theselected processing action and identifying the client device, to executethe selected processing action based at least in part on the payloaddata; based at least in part on the contextual data, cause the clientdevice to display an interactive dialog; receive additional data fromthe client device via the interactive dialog; and provide the additionaldata to the external application system to be associated with thepayload data to enable the external application system to utilize theadditional data to execute the selected processing action.
 2. The systemof claim 1, wherein the one or more processors are further configuredto: receive a confirmation response from the external application systemindicating completion of the selected processing action; and transmit aconfirmation message to the client device.
 3. The system of claim 1,wherein the file object is shared between a plurality of client deviceswithin a communication channel via the group-based communicationplatform, wherein the communication channel has an associated channelidentifier and wherein the one or more processors are further configuredto: cause the client device to display a curated list of a plurality ofprocessing actions, wherein the processing actions included within thecurated list are selected based at least in part on a channelidentifier; and receive input from the client device selecting theprocessing action from the curated list of a plurality of processingactions.
 4. The system of claim 1, wherein the file object is associatedwith one or more characteristics identifying a file object type, andwherein the one or more processors are further configured to: cause theclient device to display a cured list of a plurality of processingactions, wherein the processing actions included within the curated listare selected based at least in part on the file object type; and receiveinput from the client device selecting the processing action from thecurated list of a plurality of processing actions.
 5. The system ofclaim 1, wherein providing payload data and contextual data to theexternal application system comprises: generating a container comprisingthe contextual data and the payload data; and providing the container toa proxy endpoint stored within the group-based communication platformand accessible to the external application system to enable the externalapplication system to retrieve data within the container.
 6. The systemof claim 1, wherein the contextual data identifying the client device isembodied as a client token.
 7. The system of claim 1, wherein causingthe client device to display an interactive dialog comprises: receivinga response from the external application system; and causing the clientdevice to display the interactive dialog comprising data received as apart of the response.
 8. A computer program product for initiating aprocessing action within an external application system based at leastin part on a file object shared via a group-based communicationplatform, the computer program product comprising at least onenon-transitory computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising an executable portion configured to: store, withinone or more non-transitory memory storage repositories, a processingaction table identifying one or more processing actions available forone or more file objects; receive, from a client device, a selection ofa file object and a processing action to be performed by an externalapplication system for a selected file object, wherein a selectedprocessing action is selected from the processing action table; provide,to the external application system, payload data identifying theselected file object and contextual data identifying the selectedprocessing action and identifying the client device, to execute theselected processing action based at least in part on the payload data;based at least in part on the contextual data, cause the client deviceto display an interactive dialog; receive additional data from theclient device via the interactive dialog; and provide the additionaldata to the external application system to be associated with thepayload data to enable the external application system to utilize theadditional data to execute the selected processing action.
 9. Thecomputer program product of claim 8, further comprising an executableportion configured to: receive a confirmation response from the externalapplication system indicating completion of the selected processingaction; and transmit a confirmation message to the client device. 10.The computer program product of claim 8, wherein the file object isshared between a plurality of client devices within a communicationchannel via the group-based communication platform, wherein thecommunication channel has an associated channel identifier and whereinthe computer program product further comprises an executable portionconfigured to: cause the client device to display a curated list of aplurality of processing actions, wherein the processing actions includedwithin the curated list are selected based at least in part on a channelidentifier; and receive input from the client device selecting theprocessing action from the curated list of a plurality of processingactions.
 11. The computer program product of claim 8, wherein the fileobject is associated with one or more characteristics identifying a fileobject type, and wherein the computer program product further comprisesan executable portion configured to: cause the client device to displaya cured list of a plurality of processing actions, wherein theprocessing actions included within the curated list are selected basedat least in part on the file object type; and receive input from theclient device selecting the processing action from the curated list of aplurality of processing actions.
 12. The computer program product ofclaim 8, wherein providing payload data and contextual data to theexternal application system comprises: generating a container comprisingthe contextual data and the payload data; and providing the container toa proxy endpoint stored within the group-based communication platformand accessible to the external application system to enable the externalapplication system to retrieve data within the container.
 13. Thecomputer program product of claim 8, wherein the contextual dataidentifying the client device is embodied as a client token.
 14. Thecomputer program product of claim 8, wherein causing the client deviceto display an interactive dialog comprises: receiving a response fromthe external application system; and causing the client device todisplay the interactive dialog comprising data received as a part of theresponse.
 15. A computer-implemented method for initiating a processingaction within an external application system based at least in part on afile object shared via a group-based communication platform, wherein themethod comprises: storing, within one or more non-transitory memorystorage repositories, a processing action table identifying one or moreprocessing actions available for one or more file objects; receiving,via one or more processors and from a client device, a selection of afile object and a processing action to be performed by an externalapplication system for a selected file object, wherein a selectedprocessing action is selected from the processing action table;providing, via the one or more processors to the external applicationsystem, payload data identifying the selected file object and contextualdata identifying the selected processing action and identifying theclient device, to execute the selected processing action based at leastin part on the payload data; based at least in part on the contextualdata, causing, via the one or more processors, the client device todisplay an interactive dialog; receiving, via the one or moreprocessors, additional data from the client device via the interactivedialog; and providing, via the one or more processors, the additionaldata to the external application system to be associated with thepayload data to enable the external application system to utilize theadditional data to execute the selected processing action.
 16. Thecomputer-implemented method of claim 15, further comprising: receiving aconfirmation response from the external application system indicatingcompletion of the selected processing action; and transmitting aconfirmation message to the client device.
 17. The computer-implementedmethod of claim 15, wherein the file object is shared between aplurality of client devices within a communication channel via thegroup-based communication platform, wherein the communication channelhas an associated channel identifier and wherein thecomputer-implemented method further comprises: causing the client deviceto display a curated list of a plurality of processing actions, whereinthe processing actions included within the curated list are selectedbased at least in part on a channel identifier; and receiving input fromthe client device selecting the processing action from the curated listof a plurality of processing actions.
 18. The computer-implementedmethod of claim 15, wherein the file object is associated with one ormore characteristics identifying a file object type, and wherein thecomputer-implemented method further comprises: causing the client deviceto display a cured list of a plurality of processing actions, whereinthe processing actions included within the curated list are selectedbased at least in part on the file object type; and receiving input fromthe client device selecting the processing action from the curated listof a plurality of processing actions.
 19. The computer-implementedmethod of claim 18, wherein providing payload data and contextual datato the external application system comprises: generating a containercomprising the contextual data and the payload data; and providing thecontainer to a proxy endpoint stored within the group-basedcommunication platform and accessible to the external application systemto enable the external application system to retrieve data within thecontainer.
 20. The computer-implemented method of claim 15, wherein thecontextual data identifying the client device is embodied as a clienttoken.
 21. The computer-implemented method of claim 15, wherein causingthe client device to display an interactive dialog comprises: receivinga response from the external application system; and causing the clientdevice to display the interactive dialog comprising data received as apart of the response.